HCL
Skip to main content  
 
   


SPRTechnote


LDAP Search Never Gets a Base Entry for Subtree Search

Technote Number: 1096292


Problem:
This issue was reported to Lotus Software Quality Engineering and was first
addressed in Domino 5.0.3. It has been further addressed in Domino 5.0.4.
Re-evaluation confirms that this issue does not occur in Domino 5.0.4, 5.0.5,
and later.

Excerpt from the Lotus Notes and Lotus Domino Release 5.0.3 QMR fix list:

Internet Protocols - LDAP

SPR# YUMA4DPQLW - Fix the following LDAP filter (scope: subtree, base: CN=Test
Group,O=Test Org, filter: (|(member=CN=Test User,O=Test Org)(uniquename=CN=Test
User,O=Test Org)) ) which was preventing Websphere from using the Domino
directory for authentication. [5.0.3]

Supporting Information:

LDAP is a client-server protocol for accessing a directory service.
Notes/Domino R5 on LDAP (Lightweight Directory Access Protocol) Version 3 is
defined by Request for Comments (RFCs) 2251 - 2256.

Note: Double-byte characters are supported in LDAP Version 3. For further
information, see the document entitled "Enabling LDAP Searches Using R5
Alternative Names" (#: 171695 ).

Related Documents:

The Domino 5 Admin Help contains the following sections:






Enabling LDAP Searches Using R5 Alternative Names
Document #: 171695

Web Authentication Against Microsoft Exchange 5.5 LDAP Server Fails
Document #: 175714

LDIF & LDAP: Exporting Domino Directory Information
Document #: 177348

How to Configure a Domino R5 Server and Netscape Enterprise Server for Web
Authentication Using LDAP
Document #: 168938

LDAP v3 Proposal/Draft information can be found at the following website:

http://www.critical-angle.com/ldapworld/draft-ietf-asid-ldapv3-protocol-04.txt

Also, additional information can be found at the University of Michigan LDAP
website:

http://www.umich.edu/~dirsvcs/ldap/ldap.html
More >





  Document options
Print this document
Print view

  Search
Search Advanced Search


  Fix list views

 RSS feeds   RSS
Subscribe to the fix list

  Resources
Using this database
View notices

  HCL Support
HCL Support


    About HCL Privacy Contact